You can use an EDI job to define a schedule for N4 to execute in a specified EDI session at timed intervals.
The EDI Job should process all the files present in the EDI mailbox defined in the Inbound EDI Session at the time the EDI Job is triggered based on the schedule.
When the file is posted successfully, N4 moves the EDI files to the archive sub-directory located in the EDI mailbox.
Difference between the EDI session and manual EDI load:
|
EDI Session |
EDI Load |
|---|---|
|
Runs automatically as scheduled in the job, and automatically selects and processes all the EDI files present in the mailbox at the time the job is triggered. You can select the Execute Now (once) option to process the jobs immediately. |
Determines when to manually run the EDI session. You must select a specific EDI file to be posted or loaded. |
You can also check the Execution Logs tab for the selected job(s) to view the status or information of each job execution.
Recommendations:
- You must check each mailbox directory to make sure that each EDI mailbox is configured with a different or exclusive directory.
- For all the job groups, you must select the Assign jobs randomly within the group option from the Load Balancing Scheme LOV in the Job Groups form. As N4 does not allow you to update the already existing job groups to set the value in the Load Balancing Scheme LOV, you must create a job group and update the EDI jobs to include this job group.
- Schedule all the EDI jobs to run less frequently and at different intervals to prevent them from running at the same time.